Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 207057217fdf25c233c26c21521af22a04e7fdcbe833f2cf32740b6c10bba2bd

Tx prefix hash: 04e98513b1b31c295b65aa78eea6daeb7b45abb1ab689224bd024d792b455ebe
Tx public key: c6f5f1063c92b31e03dab20f2cfaa3b1f34fa2edbeee90ff71903c1a643a7865
Timestamp: 1695563576 Timestamp [UCT]: 2023-09-24 13:52:56 Age [y:d:h:m:s]: 01:196:13:46:00
Block: 855163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401544 RingCT/type: yes/0
Extra: 01c6f5f1063c92b31e03dab20f2cfaa3b1f34fa2edbeee90ff71903c1a643a7865021100000006faf35c9c000000000000000000

1 output(s) for total of 0.900513100000 dcy

stealth address amount amount idx
00: b444acfda5b7f7559cd7c34aee1bdf1b424a387bcbfe38239d8322911dcf4358 0.900513100000 1309167 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": 855173, "vin": [ { "gen": { "height": 855163 } } ], "vout": [ { "amount": 900513100, "target": { "key": "b444acfda5b7f7559cd7c34aee1bdf1b424a387bcbfe38239d8322911dcf4358" } } ], "extra": [ 1, 198, 245, 241, 6, 60, 146, 179, 30, 3, 218, 178, 15, 44, 250, 163, 177, 243, 79, 162, 237, 190, 238, 144, 255, 113, 144, 60, 26, 100, 58, 120, 101, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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