Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12c4e41bddc53893bb7e6c68d634051f730d2219115f3651a44e6946f1b2a458

Tx prefix hash: 33938c48e232cc88d964789720dfd523be1b7d42b3f8c83a255a5a5a87bff5e1
Tx public key: ee02c9378a8124457ec7337bad6eb2e8e426d00ba618f91dbee40dbcb352a1f1
Timestamp: 1736007575 Timestamp [UCT]: 2025-01-04 16:19:35 Age [y:d:h:m:s]: 00:351:15:54:16
Block: 1190143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248875 RingCT/type: yes/0
Extra: 01ee02c9378a8124457ec7337bad6eb2e8e426d00ba618f91dbee40dbcb352a1f1021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07787fb4e8e60756ec63283a88c3cd4d35f7d065009dccbc33e7517274fc669e 0.600000000000 1676658 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": 1190153, "vin": [ { "gen": { "height": 1190143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07787fb4e8e60756ec63283a88c3cd4d35f7d065009dccbc33e7517274fc669e" } } ], "extra": [ 1, 238, 2, 201, 55, 138, 129, 36, 69, 126, 199, 51, 123, 173, 110, 178, 232, 228, 38, 208, 11, 166, 24, 249, 29, 190, 228, 13, 188, 179, 82, 161, 241, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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