Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28006b6f070e2858bb86ce98b3b7bd5823aab1fb59d4d816ba87f57a5b55e905

Tx prefix hash: 80c5d2d44ec277a9d6c52c2cce82d0a9a06abda9bd311b9920e68192935b9738
Tx public key: 0cf64da555cf79423fdb2dea3c6c50817e5ea1c5c901e77f1cc79f7762ab2bf4
Timestamp: 1730741304 Timestamp [UCT]: 2024-11-04 17:28:24 Age [y:d:h:m:s]: 00:002:19:15:32
Block: 1146516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2015 RingCT/type: yes/0
Extra: 010cf64da555cf79423fdb2dea3c6c50817e5ea1c5c901e77f1cc79f7762ab2bf4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7c259d94c8ecfd6233e8ed8a5d52265a736a2b4e35055e26f2b55a25377bf8d 0.600000000000 1631173 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": 1146526, "vin": [ { "gen": { "height": 1146516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7c259d94c8ecfd6233e8ed8a5d52265a736a2b4e35055e26f2b55a25377bf8d" } } ], "extra": [ 1, 12, 246, 77, 165, 85, 207, 121, 66, 63, 219, 45, 234, 60, 108, 80, 129, 126, 94, 161, 197, 201, 1, 231, 127, 28, 199, 159, 119, 98, 171, 43, 244, 2, 17, 0, 0, 0, 3, 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