Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30718158f3f29a0afaf1d19d16935be64d5aeb646aa132630aeaca4cb4f0f03e

Tx prefix hash: 3bd5ca3a4ef484130135552c4feb3166cd7995845acc55c9c635f6148599c29b
Tx public key: 45c2bb0a48e52267f5b9151deed9f11e9b39010b91fbb61cd87814fae7c425f3
Timestamp: 1713796672 Timestamp [UCT]: 2024-04-22 14:37:52 Age [y:d:h:m:s]: 00:345:01:05:01
Block: 1006129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246664 RingCT/type: yes/0
Extra: 0145c2bb0a48e52267f5b9151deed9f11e9b39010b91fbb61cd87814fae7c425f302110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2919887128dc1c01b65b740faec7524b4d6d373d81a2de9740c27adfcbfdc6f9 0.600000000000 1467055 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": 1006139, "vin": [ { "gen": { "height": 1006129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2919887128dc1c01b65b740faec7524b4d6d373d81a2de9740c27adfcbfdc6f9" } } ], "extra": [ 1, 69, 194, 187, 10, 72, 229, 34, 103, 245, 185, 21, 29, 238, 217, 241, 30, 155, 57, 1, 11, 145, 251, 182, 28, 216, 120, 20, 250, 231, 196, 37, 243, 2, 17, 0, 0, 0, 9, 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