Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e463aef84736f9c330a3f5b02dce9263f690330397bb76fe1a59eacf5e41b0

Tx prefix hash: 8d0bae983f96196df3f31808b1f5965698cfa33474491e2274d2d7f3b0a497f9
Tx public key: a7001862cf55e172e69ca4699770fac251b266f545f370f932ce525b2f3a20de
Timestamp: 1707746217 Timestamp [UCT]: 2024-02-12 13:56:57 Age [y:d:h:m:s]: 01:053:10:56:31
Block: 955959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299243 RingCT/type: yes/0
Extra: 01a7001862cf55e172e69ca4699770fac251b266f545f370f932ce525b2f3a20de021100000002b6e2dc33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 089793c9c3c68a49c5baa4cb5a748362af9bcdb66d8560d47ff717af6e454454 0.600000000000 1415261 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": 955969, "vin": [ { "gen": { "height": 955959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "089793c9c3c68a49c5baa4cb5a748362af9bcdb66d8560d47ff717af6e454454" } } ], "extra": [ 1, 167, 0, 24, 98, 207, 85, 225, 114, 230, 156, 164, 105, 151, 112, 250, 194, 81, 178, 102, 245, 69, 243, 112, 249, 50, 206, 82, 91, 47, 58, 32, 222, 2, 17, 0, 0, 0, 2, 182, 226, 220, 51, 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