Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5faee2c05c3403becc9c6dddd803f04919ac800e8c011f169e82ca4569a20c0

Tx prefix hash: 4bf3d971d2ea7556c78a4336f23e5ba150df0cccee3ae708e2a7583a47dfddf2
Tx public key: 938a20e930f3801b4a506fc10da078658e73eec379f703897ab37c039607d6fa
Timestamp: 1709294862 Timestamp [UCT]: 2024-03-01 12:07:42 Age [y:d:h:m:s]: 01:037:07:05:08
Block: 968815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287643 RingCT/type: yes/0
Extra: 01938a20e930f3801b4a506fc10da078658e73eec379f703897ab37c039607d6fa0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 904300a14776f7e98176cce1fff3f02a1b321242808599e1836c4d8aefb5d11a 0.600000000000 1428638 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": 968825, "vin": [ { "gen": { "height": 968815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "904300a14776f7e98176cce1fff3f02a1b321242808599e1836c4d8aefb5d11a" } } ], "extra": [ 1, 147, 138, 32, 233, 48, 243, 128, 27, 74, 80, 111, 193, 13, 160, 120, 101, 142, 115, 238, 195, 121, 247, 3, 137, 122, 179, 124, 3, 150, 7, 214, 250, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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