Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 303b1cd77508784ba59f42a2ce1ae65f4b4268a219df2cde91d9871f56b557c5

Tx prefix hash: 898df70253553cc558baccf1d10104a3f2fc4d7968164678f91ed56491d96361
Tx public key: 1435867d48b3f10a100ba611fe1c8f2418a31a3fc7667bca8489b2be6ce26b51
Timestamp: 1648611394 Timestamp [UCT]: 2022-03-30 03:36:34 Age [y:d:h:m:s]: 02:272:23:16:02
Block: 469332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714670 RingCT/type: yes/0
Extra: 011435867d48b3f10a100ba611fe1c8f2418a31a3fc7667bca8489b2be6ce26b510211000000054da16a3a000000000000000000

1 output(s) for total of 17.096550973000 dcy

stealth address amount amount idx
00: 83c5301422f88e2f6d20e71ef40dfab0e426eca557da9b77ea7c786e4dc9a05e 17.096550973000 888258 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": 469342, "vin": [ { "gen": { "height": 469332 } } ], "vout": [ { "amount": 17096550973, "target": { "key": "83c5301422f88e2f6d20e71ef40dfab0e426eca557da9b77ea7c786e4dc9a05e" } } ], "extra": [ 1, 20, 53, 134, 125, 72, 179, 241, 10, 16, 11, 166, 17, 254, 28, 143, 36, 24, 163, 26, 63, 199, 102, 123, 202, 132, 137, 178, 190, 108, 226, 107, 81, 2, 17, 0, 0, 0, 5, 77, 161, 106, 58, 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