Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392713edefe17abbc6b710a5e819f2db30799e5ddb309a6f4c328209a4c5d51b

Tx prefix hash: 52a06d50d4cdb6a17ec2b45e6a268258ad1e7c89a4caadbcf7810a889a82d89a
Tx public key: 8e7b83b6e8fafa205abdcc437701bf0ff98944bf393f7c38c332a4b1f2decd28
Timestamp: 1718389111 Timestamp [UCT]: 2024-06-14 18:18:31 Age [y:d:h:m:s]: 00:205:14:27:34
Block: 1044208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147141 RingCT/type: yes/0
Extra: 018e7b83b6e8fafa205abdcc437701bf0ff98944bf393f7c38c332a4b1f2decd2802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ea5130fc93c63c987cd7a32f4eea3de61ecf01c85bc55ba7e47f3328d1778b3 0.600000000000 1513451 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": 1044218, "vin": [ { "gen": { "height": 1044208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ea5130fc93c63c987cd7a32f4eea3de61ecf01c85bc55ba7e47f3328d1778b3" } } ], "extra": [ 1, 142, 123, 131, 182, 232, 250, 250, 32, 90, 189, 204, 67, 119, 1, 191, 15, 249, 137, 68, 191, 57, 63, 124, 56, 195, 50, 164, 177, 242, 222, 205, 40, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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