Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58b568f1393ab1bf87fe06597e1602eea78fd69c64c8c4052e9768cbbaeb942

Tx prefix hash: 34959885fa588ca96f3910f606becddf9af76703d045e9a8fa9fe7130e3555c0
Tx public key: dc48950d9b5a85007ac8f987f27551d87e7d34a71f813c6ee5e2542892e65a08
Timestamp: 1711768959 Timestamp [UCT]: 2024-03-30 03:22:39 Age [y:d:h:m:s]: 00:230:07:22:55
Block: 989337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164859 RingCT/type: yes/0
Extra: 01dc48950d9b5a85007ac8f987f27551d87e7d34a71f813c6ee5e2542892e65a0802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3d1c4d45f08d1fd1f4e2733eaf3f4c5905485cb4df0d2a6d22c35bdb14e5822 0.600000000000 1449634 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": 989347, "vin": [ { "gen": { "height": 989337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3d1c4d45f08d1fd1f4e2733eaf3f4c5905485cb4df0d2a6d22c35bdb14e5822" } } ], "extra": [ 1, 220, 72, 149, 13, 155, 90, 133, 0, 122, 200, 249, 135, 242, 117, 81, 216, 126, 125, 52, 167, 31, 129, 60, 110, 229, 226, 84, 40, 146, 230, 90, 8, 2, 17, 0, 0, 0, 7, 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