Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4877c553c44bdb85e413552b3d78b55e38bf1359be4edc1bced61af84bfa1a4

Tx prefix hash: 8fda8a01149a97e4be97fa85a4501ee7c0837b3489e3652556edeb1e61c8d7cb
Tx public key: 64329e5bc0398ed1a400e5ad06853f36cdd9aecbd482657158be1f019e0ba7f2
Timestamp: 1717038075 Timestamp [UCT]: 2024-05-30 03:01:15 Age [y:d:h:m:s]: 00:360:11:53:11
Block: 1032994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257700 RingCT/type: yes/0
Extra: 0164329e5bc0398ed1a400e5ad06853f36cdd9aecbd482657158be1f019e0ba7f20211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e0e1382d0683b2e976ded3389df585dca8a55eef259159e4e9e1c5f5353e908 0.600000000000 1501451 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": 1033004, "vin": [ { "gen": { "height": 1032994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e0e1382d0683b2e976ded3389df585dca8a55eef259159e4e9e1c5f5353e908" } } ], "extra": [ 1, 100, 50, 158, 91, 192, 57, 142, 209, 164, 0, 229, 173, 6, 133, 63, 54, 205, 217, 174, 203, 212, 130, 101, 113, 88, 190, 31, 1, 158, 11, 167, 242, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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