Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12fea81f22bde1ba924b605170a4593bbdb359fa0762f6dee6de82ee9388d4b1

Tx prefix hash: 42964e187bc16f7b10bd1b2a171c04d997b397c40310748dc3cf4af8c100f96b
Tx public key: ac39e897ca3d1fe774429d5c9a691718e3501c51888dc6b4c86b6f9acf301831
Timestamp: 1700471021 Timestamp [UCT]: 2023-11-20 09:03:41 Age [y:d:h:m:s]: 01:354:01:49:44
Block: 895647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511949 RingCT/type: yes/0
Extra: 01ac39e897ca3d1fe774429d5c9a691718e3501c51888dc6b4c86b6f9acf30183102110000000675e3f0e9000000000000000000

1 output(s) for total of 0.661225628000 dcy

stealth address amount amount idx
00: e91d1386ae830d92955797a217a887cb463701ca12afc744af26ecfc94590098 0.661225628000 1351888 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": 895657, "vin": [ { "gen": { "height": 895647 } } ], "vout": [ { "amount": 661225628, "target": { "key": "e91d1386ae830d92955797a217a887cb463701ca12afc744af26ecfc94590098" } } ], "extra": [ 1, 172, 57, 232, 151, 202, 61, 31, 231, 116, 66, 157, 92, 154, 105, 23, 24, 227, 80, 28, 81, 136, 141, 198, 180, 200, 107, 111, 154, 207, 48, 24, 49, 2, 17, 0, 0, 0, 6, 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