Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bc2674b7a150fcaeb667d93624af17d9fa8c4e3e52939f6b17c11f23812b52a

Tx prefix hash: 7fbbc8dd9e8762a70dec0fd322251db9dbc16486b096ceb132dba6a23a66b659
Tx public key: f533f8b011a26adc1df68e2f3157f6c444a9cdaaa8609d41bd32d44f72e080ba
Timestamp: 1685350600 Timestamp [UCT]: 2023-05-29 08:56:40 Age [y:d:h:m:s]: 02:002:18:06:41
Block: 770547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524079 RingCT/type: yes/0
Extra: 01f533f8b011a26adc1df68e2f3157f6c444a9cdaaa8609d41bd32d44f72e080ba021100000001b3164c24000000000000000000

1 output(s) for total of 1.717347146000 dcy

stealth address amount amount idx
00: 20492a6935b7b36af5a622e83d9215677e25c021ab79b09add132401754cd6bd 1.717347146000 1219856 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": 770557, "vin": [ { "gen": { "height": 770547 } } ], "vout": [ { "amount": 1717347146, "target": { "key": "20492a6935b7b36af5a622e83d9215677e25c021ab79b09add132401754cd6bd" } } ], "extra": [ 1, 245, 51, 248, 176, 17, 162, 106, 220, 29, 246, 142, 47, 49, 87, 246, 196, 68, 169, 205, 170, 168, 96, 157, 65, 189, 50, 212, 79, 114, 224, 128, 186, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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