Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d44f967aa76c8f0f9b0e5f8ead43cc45b235a6c03668784311356f187bb3e44b

Tx prefix hash: 47793ab78488e65645edf6b1cc64cf87eebda86dfbfe66a6360d26c7fb3d0196
Tx public key: a188540bcd4aa2941c82d08dc2ea06e1fc68361bcaab7b4180e2a55e69fa2b77
Timestamp: 1633181123 Timestamp [UCT]: 2021-10-02 13:25:23 Age [y:d:h:m:s]: 03:089:02:09:28
Block: 345201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 840605 RingCT/type: yes/0
Extra: 01a188540bcd4aa2941c82d08dc2ea06e1fc68361bcaab7b4180e2a55e69fa2b7702110000000137cb3088000000000000000000

1 output(s) for total of 44.076410012000 dcy

stealth address amount amount idx
00: 2575032f007a3242dd2d8992b16b18effc012731edb3a951189da51ece0c34ab 44.076410012000 708139 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": 345211, "vin": [ { "gen": { "height": 345201 } } ], "vout": [ { "amount": 44076410012, "target": { "key": "2575032f007a3242dd2d8992b16b18effc012731edb3a951189da51ece0c34ab" } } ], "extra": [ 1, 161, 136, 84, 11, 205, 74, 162, 148, 28, 130, 208, 141, 194, 234, 6, 225, 252, 104, 54, 27, 202, 171, 123, 65, 128, 226, 165, 94, 105, 250, 43, 119, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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