Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31b90bb4993cd1df023c6f9bcfbb3647463137e4c3da592d35aaedb6c539c3b3

Tx prefix hash: 9deed6e5b0a38d7b02236f9419ddd7144c475176232b930c6cb08ef38d909c14
Tx public key: 8fac69e3a9f01a3a5a2c54a1a562afbdf3b2ffe3d472149ad9888288b30c432b
Timestamp: 1703824142 Timestamp [UCT]: 2023-12-29 04:29:02 Age [y:d:h:m:s]: 01:168:14:17:51
Block: 923451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381567 RingCT/type: yes/0
Extra: 018fac69e3a9f01a3a5a2c54a1a562afbdf3b2ffe3d472149ad9888288b30c432b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4cb67430e58f918c86c3ce68ee42e1e359b5f210b267b59608c109c2b2a16c2 0.600000000000 1381183 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": 923461, "vin": [ { "gen": { "height": 923451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4cb67430e58f918c86c3ce68ee42e1e359b5f210b267b59608c109c2b2a16c2" } } ], "extra": [ 1, 143, 172, 105, 227, 169, 240, 26, 58, 90, 44, 84, 161, 165, 98, 175, 189, 243, 178, 255, 227, 212, 114, 20, 154, 217, 136, 130, 136, 179, 12, 67, 43, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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