Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d32f596df1883fd0e3ec2f9bccc11d55756e6f8d18ca52c199a8dbec3cb5418

Tx prefix hash: 1fb683decfd0ce52803e3ff7f690ed08d603d42da99d06639c725278304e9772
Tx public key: 5172d0d6f220d6cd3e9893281a5d89d1065317e5e89876c473defcf2e78acbfd
Timestamp: 1722938438 Timestamp [UCT]: 2024-08-06 10:00:38 Age [y:d:h:m:s]: 00:162:02:54:30
Block: 1081914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115981 RingCT/type: yes/0
Extra: 015172d0d6f220d6cd3e9893281a5d89d1065317e5e89876c473defcf2e78acbfd02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa71bfe3aa6f4e5571990b3bd55b0c73a5ccbcb8b9d2b046214cd67759e4aad 0.600000000000 1555737 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": 1081924, "vin": [ { "gen": { "height": 1081914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa71bfe3aa6f4e5571990b3bd55b0c73a5ccbcb8b9d2b046214cd67759e4aad" } } ], "extra": [ 1, 81, 114, 208, 214, 242, 32, 214, 205, 62, 152, 147, 40, 26, 93, 137, 209, 6, 83, 23, 229, 232, 152, 118, 196, 115, 222, 252, 242, 231, 138, 203, 253, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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