Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44bbdb3c8baf6daa7ac2086b1c561dd0d2c1b4ec2cfc23d3bc93e93f1b15ae8c

Tx prefix hash: 4ba04b0d2c9ca6ef131a7f957fc50b0e37ed95a0b8332d098d2c1344cf901db5
Tx public key: f8ccd40468a2dc1b95dd7f5c0e8c8ecc82e23f72b6847a614ed86536636385a1
Timestamp: 1740066829 Timestamp [UCT]: 2025-02-20 15:53:49 Age [y:d:h:m:s]: 00:020:13:01:05
Block: 1223452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14724 RingCT/type: yes/0
Extra: 01f8ccd40468a2dc1b95dd7f5c0e8c8ecc82e23f72b6847a614ed86536636385a1021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a63b7d071dbaea592dfd6863342f4d424cf5addc239490e1fb52c17e32ca0301 0.600000000000 1710309 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": 1223462, "vin": [ { "gen": { "height": 1223452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a63b7d071dbaea592dfd6863342f4d424cf5addc239490e1fb52c17e32ca0301" } } ], "extra": [ 1, 248, 204, 212, 4, 104, 162, 220, 27, 149, 221, 127, 92, 14, 140, 142, 204, 130, 226, 63, 114, 182, 132, 122, 97, 78, 216, 101, 54, 99, 99, 133, 161, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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