Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 015ed78d86b6140f715595697d994f9d571941c4a04b2c8e04243b4df879d08a

Tx prefix hash: 506ced79736b60608c5eb4d0957422b55ba9951541f47e990f035d8828e9f11b
Tx public key: a09ddc833361abfd5e5b1732d6a16caae8b3c15116dc7a7e6b979116025227a0
Timestamp: 1702978972 Timestamp [UCT]: 2023-12-19 09:42:52 Age [y:d:h:m:s]: 01:036:00:08:07
Block: 916448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287034 RingCT/type: yes/0
Extra: 01a09ddc833361abfd5e5b1732d6a16caae8b3c15116dc7a7e6b979116025227a002110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 139c35f258270894f6e94b87f7bd2377953b040191adb38c1e7ef244cbb59504 0.600000000000 1374000 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": 916458, "vin": [ { "gen": { "height": 916448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "139c35f258270894f6e94b87f7bd2377953b040191adb38c1e7ef244cbb59504" } } ], "extra": [ 1, 160, 157, 220, 131, 51, 97, 171, 253, 94, 91, 23, 50, 214, 161, 108, 170, 232, 179, 193, 81, 22, 220, 122, 126, 107, 151, 145, 22, 2, 82, 39, 160, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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