Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d5194cf319f473ebc02130a4a31063fd6cfb630c3539dd81048d07507bf712

Tx prefix hash: f8f2f5c69c157a859cf42290c33ed32fdb1c74308c01078cb5fe0f5066629c0f
Tx public key: 28682da58c97204acce9e90f7b570f7180982e76f184c96fdc099b1913bf5a1e
Timestamp: 1652732213 Timestamp [UCT]: 2022-05-16 20:16:53 Age [y:d:h:m:s]: 02:188:04:56:02
Block: 502433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 655058 RingCT/type: yes/0
Extra: 0128682da58c97204acce9e90f7b570f7180982e76f184c96fdc099b1913bf5a1e02110000000575e3f0e9000000000000000000

1 output(s) for total of 13.281009981000 dcy

stealth address amount amount idx
00: 404f5620ed2454430642f64353508408d028efbd27db3beef3b041b542ce59e7 13.281009981000 927238 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": 502443, "vin": [ { "gen": { "height": 502433 } } ], "vout": [ { "amount": 13281009981, "target": { "key": "404f5620ed2454430642f64353508408d028efbd27db3beef3b041b542ce59e7" } } ], "extra": [ 1, 40, 104, 45, 165, 140, 151, 32, 74, 204, 233, 233, 15, 123, 87, 15, 113, 128, 152, 46, 118, 241, 132, 201, 111, 220, 9, 155, 25, 19, 191, 90, 30, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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