Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e56c8d81d03a57d01ed8969089df07c222e248658152eee37d2aa96a5bfd6a1d

Tx prefix hash: 489e3bcbcb3a91e39ff748221a981ab5041e97b40e3649a442fef6f41f608cef
Tx public key: 953b0313dd935cd6a5b26acbcb668dcf95cead9e21a279441647ccf7979ae000
Timestamp: 1578671641 Timestamp [UCT]: 2020-01-10 15:54:01 Age [y:d:h:m:s]: 05:098:12:07:46
Block: 42817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220350 RingCT/type: yes/0
Extra: 01953b0313dd935cd6a5b26acbcb668dcf95cead9e21a279441647ccf7979ae000021100000001bd0f9f9f000000000000000000

1 output(s) for total of 442.721229936000 dcy

stealth address amount amount idx
00: ce2678e0bffd3360e43e2527cc88ee2c757f77af7b88763b2e1aa6dc9a5ad998 442.721229936000 77263 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": 42827, "vin": [ { "gen": { "height": 42817 } } ], "vout": [ { "amount": 442721229936, "target": { "key": "ce2678e0bffd3360e43e2527cc88ee2c757f77af7b88763b2e1aa6dc9a5ad998" } } ], "extra": [ 1, 149, 59, 3, 19, 221, 147, 92, 214, 165, 178, 106, 203, 203, 102, 141, 207, 149, 206, 173, 158, 33, 162, 121, 68, 22, 71, 204, 247, 151, 154, 224, 0, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 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