Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2c2445d310539a17a906583ad5a3dcdf0503239ab23dd16c9d8fc1cb22f0df

Tx prefix hash: 44ad622110b72d432d568398e8948f02f1a487bd222dabdf4e478fb9bd19b4d2
Tx public key: 6e35fd2435ae7c4df00217bc453b38d85a69758fa626e397fb8731da05621e81
Timestamp: 1712581770 Timestamp [UCT]: 2024-04-08 13:09:30 Age [y:d:h:m:s]: 01:026:15:05:21
Block: 996026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280024 RingCT/type: yes/0
Extra: 016e35fd2435ae7c4df00217bc453b38d85a69758fa626e397fb8731da05621e810211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2660eb5dd7c26a7243a8f42cc4af7da103cb98373f78bfc85aa095d265299996 0.600000000000 1456442 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": 996036, "vin": [ { "gen": { "height": 996026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2660eb5dd7c26a7243a8f42cc4af7da103cb98373f78bfc85aa095d265299996" } } ], "extra": [ 1, 110, 53, 253, 36, 53, 174, 124, 77, 240, 2, 23, 188, 69, 59, 56, 216, 90, 105, 117, 143, 166, 38, 227, 151, 251, 135, 49, 218, 5, 98, 30, 129, 2, 17, 0, 0, 0, 6, 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