Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65c8e0f6893eba43326cff5c4f09c12316248b057728c490fb3ef6f3d09f3ae

Tx prefix hash: ad1c777e4eccf41aac3021e983252b370190c8ad1698d38fe53c1e3cf5e9d626
Tx public key: 8b8c09eb0aebcea4c6349e862f70fb2cdbcc32c9b54fcf3d1ae287195a0c1f80
Timestamp: 1711858350 Timestamp [UCT]: 2024-03-31 04:12:30 Age [y:d:h:m:s]: 01:224:16:55:26
Block: 990083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419254 RingCT/type: yes/0
Extra: 018b8c09eb0aebcea4c6349e862f70fb2cdbcc32c9b54fcf3d1ae287195a0c1f800211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5e28fe9df4d9782c1afdf36d7fd96c8e6825366e2cb200326d7425c25b277c1 0.600000000000 1450405 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": 990093, "vin": [ { "gen": { "height": 990083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5e28fe9df4d9782c1afdf36d7fd96c8e6825366e2cb200326d7425c25b277c1" } } ], "extra": [ 1, 139, 140, 9, 235, 10, 235, 206, 164, 198, 52, 158, 134, 47, 112, 251, 44, 219, 204, 50, 201, 181, 79, 207, 61, 26, 226, 135, 25, 90, 12, 31, 128, 2, 17, 0, 0, 0, 4, 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