Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f23747a1b7e2e068feef71c050b630783f0368453043c1939d06a8483c66cd27

Tx prefix hash: 7c41d4c56abe9f524b23fb2f0ac86d780d97d5b1518dd2c4c6b2e6e5bf98cf21
Tx public key: 9c4645d1111a5acde5a1a0e2c685dd2601a00cab3b444ead55a9393719a523fa
Timestamp: 1699128990 Timestamp [UCT]: 2023-11-04 20:16:30 Age [y:d:h:m:s]: 01:111:13:13:28
Block: 884778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340628 RingCT/type: yes/0
Extra: 019c4645d1111a5acde5a1a0e2c685dd2601a00cab3b444ead55a9393719a523fa021100000001faf35c9c000000000000000000

1 output(s) for total of 0.718394838000 dcy

stealth address amount amount idx
00: 945d0a503e728a54fa2a7e7bc02efeb6d4b41144b537e6b627787bb0eb5d4d78 0.718394838000 1340525 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": 884788, "vin": [ { "gen": { "height": 884778 } } ], "vout": [ { "amount": 718394838, "target": { "key": "945d0a503e728a54fa2a7e7bc02efeb6d4b41144b537e6b627787bb0eb5d4d78" } } ], "extra": [ 1, 156, 70, 69, 209, 17, 26, 90, 205, 229, 161, 160, 226, 198, 133, 221, 38, 1, 160, 12, 171, 59, 68, 78, 173, 85, 169, 57, 55, 25, 165, 35, 250, 2, 17, 0, 0, 0, 1, 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