Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3f72ba11a3131cbb6a1666046f88f31c7e616b7985073b94852340d3940d1ad

Tx prefix hash: 85dbc6bf2d6befdc3037885891b48e5c067127fab3ec47ebea868b07a85024fa
Tx public key: 86b1d1d92d8e75fbf8a71822232a0ec94bed52c6f4f3c163b4fa4ffb66f758db
Timestamp: 1719277563 Timestamp [UCT]: 2024-06-25 01:06:03 Age [y:d:h:m:s]: 00:216:18:34:30
Block: 1051556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154880 RingCT/type: yes/0
Extra: 0186b1d1d92d8e75fbf8a71822232a0ec94bed52c6f4f3c163b4fa4ffb66f758db0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc76661865609e244ab77bdf8a08d391927d8ceda87eaef60bf2e597626fe8f2 0.600000000000 1521869 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": 1051566, "vin": [ { "gen": { "height": 1051556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc76661865609e244ab77bdf8a08d391927d8ceda87eaef60bf2e597626fe8f2" } } ], "extra": [ 1, 134, 177, 209, 217, 45, 142, 117, 251, 248, 167, 24, 34, 35, 42, 14, 201, 75, 237, 82, 198, 244, 243, 193, 99, 180, 250, 79, 251, 102, 247, 88, 219, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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