Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2388b46aa86cfb0b46cf1b322ab9aa10ec158cb2e8435b11211984169d277ea5

Tx prefix hash: 7943de7920ebd963edcd0d7b4b58f1af8213bcf1173573005aa72a6cdcc0c00c
Tx public key: c90f2221f2061d7f74622018a88f6c00f320ac47d38c8e8e2060eecefd602cec
Timestamp: 1705008478 Timestamp [UCT]: 2024-01-11 21:27:58 Age [y:d:h:m:s]: 01:105:06:32:37
Block: 933250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336355 RingCT/type: yes/0
Extra: 01c90f2221f2061d7f74622018a88f6c00f320ac47d38c8e8e2060eecefd602cec02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 910305416e51101fb312d75fde1022a1d0acc61d0e57ba1b31742c89a85cc65a 0.600000000000 1391210 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": 933260, "vin": [ { "gen": { "height": 933250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "910305416e51101fb312d75fde1022a1d0acc61d0e57ba1b31742c89a85cc65a" } } ], "extra": [ 1, 201, 15, 34, 33, 242, 6, 29, 127, 116, 98, 32, 24, 168, 143, 108, 0, 243, 32, 172, 71, 211, 140, 142, 142, 32, 96, 238, 206, 253, 96, 44, 236, 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