Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de90d7db52000275221988035dc161abf94afb220678702da606608e8cb889b

Tx prefix hash: 7c41f563e29db859cb1d84c1b5f913e66ea69c33c2297b09806991be3873edd8
Tx public key: 73a4ae0f067188b84b2f4b28698bb4a590f3383d38d89dbb5a4f1dda1e2760a3
Timestamp: 1578821342 Timestamp [UCT]: 2020-01-12 09:29:02 Age [y:d:h:m:s]: 05:052:22:08:26
Block: 43828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187985 RingCT/type: yes/0
Extra: 0173a4ae0f067188b84b2f4b28698bb4a590f3383d38d89dbb5a4f1dda1e2760a302110000000ad81c26c0000000000000000000

1 output(s) for total of 439.327083549000 dcy

stealth address amount amount idx
00: 3f74b9ed7a7cb74885f92ae8defe1f37a8e2cb8b82229f7ebff86f5edf2bd49e 439.327083549000 79517 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": 43838, "vin": [ { "gen": { "height": 43828 } } ], "vout": [ { "amount": 439327083549, "target": { "key": "3f74b9ed7a7cb74885f92ae8defe1f37a8e2cb8b82229f7ebff86f5edf2bd49e" } } ], "extra": [ 1, 115, 164, 174, 15, 6, 113, 136, 184, 75, 47, 75, 40, 105, 139, 180, 165, 144, 243, 56, 61, 56, 216, 157, 187, 90, 79, 29, 218, 30, 39, 96, 163, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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