Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0385e1e3825ab6e2b14d26ae7768e4582a9ddba6580845b62d1cb549aecac65e

Tx prefix hash: 31879cc1e7236eff7df4a2ed9191b006c2b6be8c83f4a18c9c286c355d187669
Tx public key: e9ca09374dad55f992dc402a64ea1c2c8999353e4d4b93c6211cf4c3660bdc9f
Timestamp: 1648526342 Timestamp [UCT]: 2022-03-29 03:59:02 Age [y:d:h:m:s]: 02:272:01:28:00
Block: 468659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714003 RingCT/type: yes/0
Extra: 01e9ca09374dad55f992dc402a64ea1c2c8999353e4d4b93c6211cf4c3660bdc9f02110000000306faf294000000000000000000

1 output(s) for total of 17.184560714000 dcy

stealth address amount amount idx
00: b085a6eb5294b0e0df31f9b5e47459029e7d97b02116e5b63674c5e564cfa71a 17.184560714000 887421 of 0

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": 468669, "vin": [ { "gen": { "height": 468659 } } ], "vout": [ { "amount": 17184560714, "target": { "key": "b085a6eb5294b0e0df31f9b5e47459029e7d97b02116e5b63674c5e564cfa71a" } } ], "extra": [ 1, 233, 202, 9, 55, 77, 173, 85, 249, 146, 220, 64, 42, 100, 234, 28, 44, 137, 153, 53, 62, 77, 75, 147, 198, 33, 28, 244, 195, 102, 11, 220, 159, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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