Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9639fab8fe7c8b199a112939dc4f5af0f0bb325347de4ca8e5340578f88f0909

Tx prefix hash: 60c64206fdd26232cb3977eca943ed790a4623887bd9c114504af137df08033d
Tx public key: d474943bf4bdd3c881106c2bc7a2b595018f493d30c88d8c503772443f29abfe
Timestamp: 1704655847 Timestamp [UCT]: 2024-01-07 19:30:47 Age [y:d:h:m:s]: 01:151:12:33:19
Block: 930320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369460 RingCT/type: yes/0
Extra: 01d474943bf4bdd3c881106c2bc7a2b595018f493d30c88d8c503772443f29abfe02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30e7a8d99fbcf06ac9bcb8a3c5210bc05aaa0f210e1e7f1cc26a69aebcab6c3e 0.600000000000 1388202 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": 930330, "vin": [ { "gen": { "height": 930320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30e7a8d99fbcf06ac9bcb8a3c5210bc05aaa0f210e1e7f1cc26a69aebcab6c3e" } } ], "extra": [ 1, 212, 116, 148, 59, 244, 189, 211, 200, 129, 16, 108, 43, 199, 162, 181, 149, 1, 143, 73, 61, 48, 200, 141, 140, 80, 55, 114, 68, 63, 41, 171, 254, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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