Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bf361573b7f8a8255dc17748980038dce412a9348178513b51723e9ded9258c

Tx prefix hash: cb05042a0275533b4b883d8cb496067ee45e5d2b85146874fb61230ef2e3cf07
Tx public key: 5669396b2c8401b090af08c84bddfcef326b8ba06c947aa22d175484fc17a5ba
Timestamp: 1695442225 Timestamp [UCT]: 2023-09-23 04:10:25 Age [y:d:h:m:s]: 02:042:21:35:54
Block: 854153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550309 RingCT/type: yes/0
Extra: 015669396b2c8401b090af08c84bddfcef326b8ba06c947aa22d175484fc17a5ba02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.907479004000 dcy

stealth address amount amount idx
00: f265d6fb00f28fdb5af19872d7a1a403ab3602cb364d4503626b847b9cbda740 0.907479004000 1308111 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": 854163, "vin": [ { "gen": { "height": 854153 } } ], "vout": [ { "amount": 907479004, "target": { "key": "f265d6fb00f28fdb5af19872d7a1a403ab3602cb364d4503626b847b9cbda740" } } ], "extra": [ 1, 86, 105, 57, 107, 44, 132, 1, 176, 144, 175, 8, 200, 75, 221, 252, 239, 50, 107, 139, 160, 108, 148, 122, 162, 45, 23, 84, 132, 252, 23, 165, 186, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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