Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62b22aa6594420f8ac750e79e21ce801f22107d13da2be875b64f41ad1b47ba3

Tx prefix hash: eb08f04051806b479255d62d89d947191261b43eaa9e8d949a00732b5ebc5c2c
Tx public key: f147ac8e9392d95a50cf80e122b02c6eaa3847f9ef5a51a395d8bbe834f0d364
Timestamp: 1706485293 Timestamp [UCT]: 2024-01-28 23:41:33 Age [y:d:h:m:s]: 01:067:14:02:47
Block: 945487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309387 RingCT/type: yes/0
Extra: 01f147ac8e9392d95a50cf80e122b02c6eaa3847f9ef5a51a395d8bbe834f0d3640211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df1e763bd83b98f65a110f55c7047bc5ebec62c73a9cbf7e71eb6af75f0b1c98 0.600000000000 1403801 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": 945497, "vin": [ { "gen": { "height": 945487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df1e763bd83b98f65a110f55c7047bc5ebec62c73a9cbf7e71eb6af75f0b1c98" } } ], "extra": [ 1, 241, 71, 172, 142, 147, 146, 217, 90, 80, 207, 128, 225, 34, 176, 44, 110, 170, 56, 71, 249, 239, 90, 81, 163, 149, 216, 187, 232, 52, 240, 211, 100, 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