Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f9e6a5afc579fa10c3d003867be0b0284d802912c771c45db08621c37a5382

Tx prefix hash: 10a66345e6b6345ff3b833617541f654bac1d20fced57b390e42d0577d4b44e8
Tx public key: deb58d338107d8ccb7d408efae93286cb2f3fdc53504d5647e2bd369f552e3fd
Timestamp: 1709730758 Timestamp [UCT]: 2024-03-06 13:12:38 Age [y:d:h:m:s]: 01:274:00:10:10
Block: 972434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454578 RingCT/type: yes/0
Extra: 01deb58d338107d8ccb7d408efae93286cb2f3fdc53504d5647e2bd369f552e3fd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6fa7cec5e18ff4ca9defed313a5f4671599c64e2f22ce2baab89c5cef88298e 0.600000000000 1432347 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": 972444, "vin": [ { "gen": { "height": 972434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6fa7cec5e18ff4ca9defed313a5f4671599c64e2f22ce2baab89c5cef88298e" } } ], "extra": [ 1, 222, 181, 141, 51, 129, 7, 216, 204, 183, 212, 8, 239, 174, 147, 40, 108, 178, 243, 253, 197, 53, 4, 213, 100, 126, 43, 211, 105, 245, 82, 227, 253, 2, 17, 0, 0, 0, 4, 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