Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 554ba987287006aaf12d412f5717f2eb14227eeba9ba6f6eb62273e2d6b7d18e

Tx prefix hash: f6dd546464f5d9cf77e675d21f8b49d7431c3ca85a802ec47422c5091484df72
Tx public key: f82bde02cff46fb7968c59fa6c4f10da95427d472340cb08dda7d9b43c2ec063
Timestamp: 1719455244 Timestamp [UCT]: 2024-06-27 02:27:24 Age [y:d:h:m:s]: 00:339:14:27:45
Block: 1053030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242724 RingCT/type: yes/0
Extra: 01f82bde02cff46fb7968c59fa6c4f10da95427d472340cb08dda7d9b43c2ec0630211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87d35d98c6481636f809da2c4b13e5746fa3ead1499d228ae7fb895fb32acef7 0.600000000000 1523375 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": 1053040, "vin": [ { "gen": { "height": 1053030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87d35d98c6481636f809da2c4b13e5746fa3ead1499d228ae7fb895fb32acef7" } } ], "extra": [ 1, 248, 43, 222, 2, 207, 244, 111, 183, 150, 140, 89, 250, 108, 79, 16, 218, 149, 66, 125, 71, 35, 64, 203, 8, 221, 167, 217, 180, 60, 46, 192, 99, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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