Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c778af49757e6e8694d679bc23609c4e3b8e6c46d237fe8a1be65cb6871b4ba6

Tx prefix hash: 759b3a6e8c6203e4022351ff602ba5e3fc5e9c71b38692e7aba2ab04da54a36d
Tx public key: 24a3faefcaf18fe9c15c208e33f5755fb2863f86a275a37497f7d02622570d76
Timestamp: 1725919721 Timestamp [UCT]: 2024-09-09 22:08:41 Age [y:d:h:m:s]: 00:209:06:12:46
Block: 1106633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149383 RingCT/type: yes/0
Extra: 0124a3faefcaf18fe9c15c208e33f5755fb2863f86a275a37497f7d02622570d76021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9ae914de7724a2e2faae9e5d48b00c30de58564d30132fb5437ef310fb97204 0.600000000000 1584234 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": 1106643, "vin": [ { "gen": { "height": 1106633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9ae914de7724a2e2faae9e5d48b00c30de58564d30132fb5437ef310fb97204" } } ], "extra": [ 1, 36, 163, 250, 239, 202, 241, 143, 233, 193, 92, 32, 142, 51, 245, 117, 95, 178, 134, 63, 134, 162, 117, 163, 116, 151, 247, 208, 38, 34, 87, 13, 118, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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