Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248c0a25bb46bf375d2da2758e73ed06710e33558be96bc877ed43c7d952919a

Tx prefix hash: e112ffc8bc47206e8cf2352b8dd9441adfb5ba601ba27a41d76430f70e8109c9
Tx public key: 1456ab90a9272f26222d2fb5aacc03b9b2cafa09a9b437e149bd2aa6169a08d7
Timestamp: 1726211745 Timestamp [UCT]: 2024-09-13 07:15:45 Age [y:d:h:m:s]: 00:055:20:04:11
Block: 1109046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39916 RingCT/type: yes/0
Extra: 011456ab90a9272f26222d2fb5aacc03b9b2cafa09a9b437e149bd2aa6169a08d7021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2cb0b2f157aef1f9562a79f41e17eaa80e7ac1abfc0865abd0fa2ec5ea525aa 0.600000000000 1587159 of 15

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": 1109056, "vin": [ { "gen": { "height": 1109046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2cb0b2f157aef1f9562a79f41e17eaa80e7ac1abfc0865abd0fa2ec5ea525aa" } } ], "extra": [ 1, 20, 86, 171, 144, 169, 39, 47, 38, 34, 45, 47, 181, 170, 204, 3, 185, 178, 202, 250, 9, 169, 180, 55, 225, 73, 189, 42, 166, 22, 154, 8, 215, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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