Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ed20274592f31e30b21ecc2924271564eebb28f3987448342c1bce46e644bb

Tx prefix hash: 70afb35731d134f8c097f27e82b8e30894a12ccaeb554574ea388c1e0dd084a8
Tx public key: 05914e40ae876f0a0a19bd6fbf2be7a1555d36e7776530186e0b75fc25de45b6
Timestamp: 1696916357 Timestamp [UCT]: 2023-10-10 05:39:17 Age [y:d:h:m:s]: 01:098:18:33:00
Block: 866386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331845 RingCT/type: yes/0
Extra: 0105914e40ae876f0a0a19bd6fbf2be7a1555d36e7776530186e0b75fc25de45b60211000000044b8f5122000000000000000000

1 output(s) for total of 0.826615531000 dcy

stealth address amount amount idx
00: a51a1e4e81351f5a0b5a09e48ea67fecbb3d89ea1127434cbd06cbd204da3b82 0.826615531000 1320976 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": 866396, "vin": [ { "gen": { "height": 866386 } } ], "vout": [ { "amount": 826615531, "target": { "key": "a51a1e4e81351f5a0b5a09e48ea67fecbb3d89ea1127434cbd06cbd204da3b82" } } ], "extra": [ 1, 5, 145, 78, 64, 174, 135, 111, 10, 10, 25, 189, 111, 191, 43, 231, 161, 85, 93, 54, 231, 119, 101, 48, 24, 110, 11, 117, 252, 37, 222, 69, 182, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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