Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb355b286c5c3a279a499a56e65a80a8a31c99ff0ee745dbf5e8246ed5b6b013

Tx prefix hash: bf177c7c8fa214648fe44c1287239eb509006af512613a08dd7d430dc46f7bcf
Tx public key: 2db731d94ed4e9cae03e722e0fc365365822583ebb70d43ee2624d1a4a283597
Timestamp: 1672915699 Timestamp [UCT]: 2023-01-05 10:48:19 Age [y:d:h:m:s]: 01:332:09:18:46
Block: 668060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498587 RingCT/type: yes/0
Extra: 012db731d94ed4e9cae03e722e0fc365365822583ebb70d43ee2624d1a4a28359702110000000652542ceb000000000000000000

1 output(s) for total of 3.753529688000 dcy

stealth address amount amount idx
00: e18a358e2db3581324e758d246b003fb2bbb4f0e743e9e726d68b5bb06cc846b 3.753529688000 1109293 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": 668070, "vin": [ { "gen": { "height": 668060 } } ], "vout": [ { "amount": 3753529688, "target": { "key": "e18a358e2db3581324e758d246b003fb2bbb4f0e743e9e726d68b5bb06cc846b" } } ], "extra": [ 1, 45, 183, 49, 217, 78, 212, 233, 202, 224, 62, 114, 46, 15, 195, 101, 54, 88, 34, 88, 62, 187, 112, 212, 62, 226, 98, 77, 26, 74, 40, 53, 151, 2, 17, 0, 0, 0, 6, 82, 84, 44, 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