Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 981731ffcb6063f0859b37d1e634ac922152913e191b2701c0dad8d82155afa3

Tx prefix hash: 08166b05fc5f0451b07d092310e7a68f1145fb99bdf9c2a85b3fb872befe476c
Tx public key: 8d560e63ce57c7defd0a819c87283df117c0bcaaf8e798d5201451abb465d30d
Timestamp: 1717737921 Timestamp [UCT]: 2024-06-07 05:25:21 Age [y:d:h:m:s]: 00:229:23:42:32
Block: 1038807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164541 RingCT/type: yes/0
Extra: 018d560e63ce57c7defd0a819c87283df117c0bcaaf8e798d5201451abb465d30d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fadf37fef940b7efd40f8c1a0d3cd81f5909e7cd4df0551384893b5470cf4fe 0.600000000000 1507368 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": 1038817, "vin": [ { "gen": { "height": 1038807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fadf37fef940b7efd40f8c1a0d3cd81f5909e7cd4df0551384893b5470cf4fe" } } ], "extra": [ 1, 141, 86, 14, 99, 206, 87, 199, 222, 253, 10, 129, 156, 135, 40, 61, 241, 23, 192, 188, 170, 248, 231, 152, 213, 32, 20, 81, 171, 180, 101, 211, 13, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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