Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abc18bb77eee67e6e524c8ed0a8db3459bd8fa10260ca3c5ae86574be387c10b

Tx prefix hash: 4e01ccbea029bfe4c8f549163764a8ef40a856769014753fd31f0d227b3a42a8
Tx public key: 358cbbc77a6b8bd00d1c29bc3b7dff6ac67c9af362202a1c4cfbe9cdfc885379
Timestamp: 1700849254 Timestamp [UCT]: 2023-11-24 18:07:34 Age [y:d:h:m:s]: 01:097:13:02:56
Block: 898789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330852 RingCT/type: yes/0
Extra: 01358cbbc77a6b8bd00d1c29bc3b7dff6ac67c9af362202a1c4cfbe9cdfc885379021100000009faf35c9c000000000000000000

1 output(s) for total of 0.645563434000 dcy

stealth address amount amount idx
00: 7f0c8dc95c4f36da3b7afe2cb8b3cc0a8b250afdcc41f3ef78c6b38251c8b9e0 0.645563434000 1355224 of 0

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": 898799, "vin": [ { "gen": { "height": 898789 } } ], "vout": [ { "amount": 645563434, "target": { "key": "7f0c8dc95c4f36da3b7afe2cb8b3cc0a8b250afdcc41f3ef78c6b38251c8b9e0" } } ], "extra": [ 1, 53, 140, 187, 199, 122, 107, 139, 208, 13, 28, 41, 188, 59, 125, 255, 106, 198, 124, 154, 243, 98, 32, 42, 28, 76, 251, 233, 205, 252, 136, 83, 121, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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