Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6be61332de577a83f6248988bc912737d141d7e96865566db8f9b7104fea8a

Tx prefix hash: c32621eeeff6c2b39177dd70996fb07afb2047ea7df6ac0793d2bc1e34196390
Tx public key: 6a7a735797b6460c8ffc34cbe7bc70091fa32533c5497f4138a28f9cd551ffb4
Timestamp: 1704675020 Timestamp [UCT]: 2024-01-08 00:50:20 Age [y:d:h:m:s]: 01:143:06:26:06
Block: 930479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363562 RingCT/type: yes/0
Extra: 016a7a735797b6460c8ffc34cbe7bc70091fa32533c5497f4138a28f9cd551ffb40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bacc429f401d69c19f57886e6fd435f3c8a0b5658e6e1e1f919164cb95399da7 0.600000000000 1388361 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": 930489, "vin": [ { "gen": { "height": 930479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bacc429f401d69c19f57886e6fd435f3c8a0b5658e6e1e1f919164cb95399da7" } } ], "extra": [ 1, 106, 122, 115, 87, 151, 182, 70, 12, 143, 252, 52, 203, 231, 188, 112, 9, 31, 163, 37, 51, 197, 73, 127, 65, 56, 162, 143, 156, 213, 81, 255, 180, 2, 17, 0, 0, 0, 1, 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