Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16ae7fc1ca512e1bd75577f0eab18ed517f5e7054cd829e823b6049af9d17732

Tx prefix hash: a1ea2ca4df5820514e7aaed11f464a476bac098634d5fea45881b42432589192
Tx public key: affc2724b5d1a422f1db5b0c79834ff50829e296fe3b1b3ddbb18defc66f5bfc
Timestamp: 1732215999 Timestamp [UCT]: 2024-11-21 19:06:39 Age [y:d:h:m:s]: 00:123:16:23:09
Block: 1158732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88206 RingCT/type: yes/0
Extra: 01affc2724b5d1a422f1db5b0c79834ff50829e296fe3b1b3ddbb18defc66f5bfc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2573f77f0adb6628dcbf3f08be37d754bb7fed3fbf187a60ad3cd2caad76971b 0.600000000000 1644361 of 15

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": 1158742, "vin": [ { "gen": { "height": 1158732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2573f77f0adb6628dcbf3f08be37d754bb7fed3fbf187a60ad3cd2caad76971b" } } ], "extra": [ 1, 175, 252, 39, 36, 181, 209, 164, 34, 241, 219, 91, 12, 121, 131, 79, 245, 8, 41, 226, 150, 254, 59, 27, 61, 219, 177, 141, 239, 198, 111, 91, 252, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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