Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1730b097f1c54c8514391aea75e1ebf18fbb615e215a5919ae044d5813143fbf

Tx prefix hash: d7e57d3580a66bb13a6444f15038a23dc42e8fd0dc4c693602a8d50b70d249c9
Tx public key: 2116481ed87a66c64c1e0df5ad28c8fffe63326aa97e1bb207f9dcf41660b216
Timestamp: 1711724088 Timestamp [UCT]: 2024-03-29 14:54:48 Age [y:d:h:m:s]: 01:044:13:24:32
Block: 988965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292813 RingCT/type: yes/0
Extra: 012116481ed87a66c64c1e0df5ad28c8fffe63326aa97e1bb207f9dcf41660b21602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efaa50ca50974bf9fd9c331416c2e58707c46235837706e3fa502ee2623d5a12 0.600000000000 1449256 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": 988975, "vin": [ { "gen": { "height": 988965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efaa50ca50974bf9fd9c331416c2e58707c46235837706e3fa502ee2623d5a12" } } ], "extra": [ 1, 33, 22, 72, 30, 216, 122, 102, 198, 76, 30, 13, 245, 173, 40, 200, 255, 254, 99, 50, 106, 169, 126, 27, 178, 7, 249, 220, 244, 22, 96, 178, 22, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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