Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 408a8a7d21b746c950efeb4cba4c9c64659cf63675ab5f1bedda4b7276ac0899

Tx prefix hash: 702c65115bfdd4827aeaf337a19d69f18bc6f5a48098087a53edf55fbb7c3552
Tx public key: 70efb605819eeb817095ea8fdb0ac9d5a6450d8e8fcadc43f3a878bd1e7a6ea2
Timestamp: 1663406798 Timestamp [UCT]: 2022-09-17 09:26:38 Age [y:d:h:m:s]: 02:192:17:46:46
Block: 589793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 659042 RingCT/type: yes/0
Extra: 0170efb605819eeb817095ea8fdb0ac9d5a6450d8e8fcadc43f3a878bd1e7a6ea202110000000275e3f0e9000000000000000000

1 output(s) for total of 6.819790460000 dcy

stealth address amount amount idx
00: c6cfd8edbd21aa810de8c354e4b716fb2fa10aa3a1c2a8081c81780be318a282 6.819790460000 1024138 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": 589803, "vin": [ { "gen": { "height": 589793 } } ], "vout": [ { "amount": 6819790460, "target": { "key": "c6cfd8edbd21aa810de8c354e4b716fb2fa10aa3a1c2a8081c81780be318a282" } } ], "extra": [ 1, 112, 239, 182, 5, 129, 158, 235, 129, 112, 149, 234, 143, 219, 10, 201, 213, 166, 69, 13, 142, 143, 202, 220, 67, 243, 168, 120, 189, 30, 122, 110, 162, 2, 17, 0, 0, 0, 2, 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