Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c86c57218a98191dd3136ce8fe50d6333e0792539ee32b15e488fce090052c0a

Tx prefix hash: b22cccef9f658ad676ae87d5b2120ada1ed1c9295cc9189fdc43d4f5d7c2e07b
Tx public key: b7208273bbee2d6458fc1c6cd736e2f90e143d803f8b36bb45fd6f20f25d12d4
Timestamp: 1631762156 Timestamp [UCT]: 2021-09-16 03:15:56 Age [y:d:h:m:s]: 03:051:05:25:12
Block: 334687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 812288 RingCT/type: yes/0
Extra: 01b7208273bbee2d6458fc1c6cd736e2f90e143d803f8b36bb45fd6f20f25d12d40211000000135d7cc334000000000000000000

1 output(s) for total of 47.757707740000 dcy

stealth address amount amount idx
00: 70b2d5f49a502010db4dfcd629fa0956c85663c970404733fd94a56f6197325f 47.757707740000 690220 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": 334697, "vin": [ { "gen": { "height": 334687 } } ], "vout": [ { "amount": 47757707740, "target": { "key": "70b2d5f49a502010db4dfcd629fa0956c85663c970404733fd94a56f6197325f" } } ], "extra": [ 1, 183, 32, 130, 115, 187, 238, 45, 100, 88, 252, 28, 108, 215, 54, 226, 249, 14, 20, 61, 128, 63, 139, 54, 187, 69, 253, 111, 32, 242, 93, 18, 212, 2, 17, 0, 0, 0, 19, 93, 124, 195, 52, 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