Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab933294f122be54f23bc2344c2e2052c8131e47114e5094d651cff5a20a39c9

Tx prefix hash: f0b92177201b14aa77a649e88c06844fdd163409e0a61888d15786cedec87ecb
Tx public key: 1a305f6c5e8d5b25fb11d53d1169a7253fe3a8b3e3c7b80760ce70ac5b649c93
Timestamp: 1710457700 Timestamp [UCT]: 2024-03-14 23:08:20 Age [y:d:h:m:s]: 01:016:19:20:12
Block: 978464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272977 RingCT/type: yes/0
Extra: 011a305f6c5e8d5b25fb11d53d1169a7253fe3a8b3e3c7b80760ce70ac5b649c9302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a15bb0a348ef916030b10ff5dcbc000abe78a54713e1af34f878dd0f1f1e0e0 0.600000000000 1438491 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": 978474, "vin": [ { "gen": { "height": 978464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a15bb0a348ef916030b10ff5dcbc000abe78a54713e1af34f878dd0f1f1e0e0" } } ], "extra": [ 1, 26, 48, 95, 108, 94, 141, 91, 37, 251, 17, 213, 61, 17, 105, 167, 37, 63, 227, 168, 179, 227, 199, 184, 7, 96, 206, 112, 172, 91, 100, 156, 147, 2, 17, 0, 0, 0, 3, 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