Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3542e89f46a28cba6054838be7d4647864887f11add8f68fa9f437c0eda67207

Tx prefix hash: ff13fb789d519872d6be5580e7becc60673be711ae5a4969f3b79e7edbe9ead2
Tx public key: e9363e912073bc603ca8502a9813ecf877a137e3a849c1affb44cff66d196a2d
Timestamp: 1579445658 Timestamp [UCT]: 2020-01-19 14:54:18 Age [y:d:h:m:s]: 04:314:20:40:56
Block: 49222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114308 RingCT/type: yes/0
Extra: 01e9363e912073bc603ca8502a9813ecf877a137e3a849c1affb44cff66d196a2d021100000001dcee4b4d000000000000000000

1 output(s) for total of 421.616679196000 dcy

stealth address amount amount idx
00: 233b8e4b36ae7953f7387e59cd3db2b24ae7e10a961a879ae7f749e83328660d 421.616679196000 91236 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": 49232, "vin": [ { "gen": { "height": 49222 } } ], "vout": [ { "amount": 421616679196, "target": { "key": "233b8e4b36ae7953f7387e59cd3db2b24ae7e10a961a879ae7f749e83328660d" } } ], "extra": [ 1, 233, 54, 62, 145, 32, 115, 188, 96, 60, 168, 80, 42, 152, 19, 236, 248, 119, 161, 55, 227, 168, 73, 193, 175, 251, 68, 207, 246, 109, 25, 106, 45, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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