Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2bd515312b0e2a3db9c6dd40b236fd9938b368fb26f91c859c52fe57627d91

Tx prefix hash: e66a7eacba26374757619fe64554de62e7f4decd949880c9d4b8a18023b48b78
Tx public key: 8f511d66c68579499a650b80c096ece14f63b75213f8581fc14a52af7c646c01
Timestamp: 1704473449 Timestamp [UCT]: 2024-01-05 16:50:49 Age [y:d:h:m:s]: 01:127:01:38:41
Block: 928816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351955 RingCT/type: yes/0
Extra: 018f511d66c68579499a650b80c096ece14f63b75213f8581fc14a52af7c646c0102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c2f0dc3a6e5b65d5fce6a0d04c93d9ef33c694aca9ba7775c4005dbf4fb192e 0.600000000000 1386680 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": 928826, "vin": [ { "gen": { "height": 928816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c2f0dc3a6e5b65d5fce6a0d04c93d9ef33c694aca9ba7775c4005dbf4fb192e" } } ], "extra": [ 1, 143, 81, 29, 102, 198, 133, 121, 73, 154, 101, 11, 128, 192, 150, 236, 225, 79, 99, 183, 82, 19, 248, 88, 31, 193, 74, 82, 175, 124, 100, 108, 1, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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