Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c2bcf9c5343a45384abffb2d8375270d171ccb3e93ec2164611a81972a657c8

Tx prefix hash: c3c2ef59c00c3732b20499c5c799b72c57296659b70330a61adb1f1318d264c2
Tx public key: 9775d8a0af49daf64f03ef2b9a2142cc1e5bc237e1b0c3cebdea6142a5715ce9
Timestamp: 1712298895 Timestamp [UCT]: 2024-04-05 06:34:55 Age [y:d:h:m:s]: 01:022:06:42:05
Block: 993681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276926 RingCT/type: yes/0
Extra: 019775d8a0af49daf64f03ef2b9a2142cc1e5bc237e1b0c3cebdea6142a5715ce90211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b399353a1096b3496f6575baa3d9398fcdcc74f4f740e3853fd5ec6aa4029da3 0.600000000000 1454069 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": 993691, "vin": [ { "gen": { "height": 993681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b399353a1096b3496f6575baa3d9398fcdcc74f4f740e3853fd5ec6aa4029da3" } } ], "extra": [ 1, 151, 117, 216, 160, 175, 73, 218, 246, 79, 3, 239, 43, 154, 33, 66, 204, 30, 91, 194, 55, 225, 176, 195, 206, 189, 234, 97, 66, 165, 113, 92, 233, 2, 17, 0, 0, 0, 2, 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