Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46349e822ba7eb7f2dd870174db9fd85dc73144101fa9424c74b6631a0a17a95

Tx prefix hash: 170276b87cc4bbeb62c3338d125eeed3ccab391f20e6cf68eea49c7a39ea1b9d
Tx public key: 2328c4542f5664393c1f68aa66b5c17f8e417602c6e8050a4afd79f11c0c0457
Timestamp: 1744558543 Timestamp [UCT]: 2025-04-13 15:35:43 Age [y:d:h:m:s]: 00:218:16:32:08
Block: 1260661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154013 RingCT/type: yes/0
Extra: 012328c4542f5664393c1f68aa66b5c17f8e417602c6e8050a4afd79f11c0c045702110000000a6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aadfd8799f193a3e11361fe118954e95b943ac424104ece2069102ea705d97e8 0.600000000000 1747822 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": 1260671, "vin": [ { "gen": { "height": 1260661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aadfd8799f193a3e11361fe118954e95b943ac424104ece2069102ea705d97e8" } } ], "extra": [ 1, 35, 40, 196, 84, 47, 86, 100, 57, 60, 31, 104, 170, 102, 181, 193, 127, 142, 65, 118, 2, 198, 232, 5, 10, 74, 253, 121, 241, 28, 12, 4, 87, 2, 17, 0, 0, 0, 10, 108, 152, 170, 61, 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