Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 31824f3b5ca8f2297abfed0d2fca9860a51de0aa319ae3372fa9c556046e53c2

Tx prefix hash: 1e9ff0293eb13e794c57760f3241748147b47e8b831aecfd4a75cfa5b6ba8c4c
Tx public key: 0e27e4bc11c63c7d06f066387e735438187d349d20e4da90c712f9ca2290844b
Timestamp: 1574947210 Timestamp [UCT]: 2019-11-28 13:20:10 Age [y:d:h:m:s]: 05:033:03:40:48
Block: 19029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166831 RingCT/type: yes/0
Extra: 010e27e4bc11c63c7d06f066387e735438187d349d20e4da90c712f9ca2290844b021100000010a47741aa000000000000000000

1 output(s) for total of 530.823207562000 dcy

stealth address amount amount idx
00: 360b2db33033761b11c3e4364eb04301ef86a044b75e44bb08db67e0e16c2d18 530.823207562000 29810 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 19039, "vin": [ { "gen": { "height": 19029 } } ], "vout": [ { "amount": 530823207562, "target": { "key": "360b2db33033761b11c3e4364eb04301ef86a044b75e44bb08db67e0e16c2d18" } } ], "extra": [ 1, 14, 39, 228, 188, 17, 198, 60, 125, 6, 240, 102, 56, 126, 115, 84, 56, 24, 125, 52, 157, 32, 228, 218, 144, 199, 18, 249, 202, 34, 144, 132, 75, 2, 17, 0, 0, 0, 16, 164, 119, 65, 170, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8