Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 527023d4f87e590f4b35a78d18b423c6e5b189802f34195ed09cbdf40a1b0eb3

Tx prefix hash: 428a6fbc2770684ae95c8467dc728b1dd3850eb0adadf9371a3846fedd4a4905
Tx public key: e2abfefeed5e0f23441f335ccf036275deb5f8bc45ac2bcb9acab4db8666997d
Timestamp: 1684904072 Timestamp [UCT]: 2023-05-24 04:54:32 Age [y:d:h:m:s]: 01:193:15:48:43
Block: 766848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399822 RingCT/type: yes/0
Extra: 01e2abfefeed5e0f23441f335ccf036275deb5f8bc45ac2bcb9acab4db8666997d02110000000afaf35c9c000000000000000000

1 output(s) for total of 1.766503168000 dcy

stealth address amount amount idx
00: 63f7ab00c8d5d7aea774d7a39439fd72ff2eb1a8b7271cba573c7b62e2ec824e 1.766503168000 1215913 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": 766858, "vin": [ { "gen": { "height": 766848 } } ], "vout": [ { "amount": 1766503168, "target": { "key": "63f7ab00c8d5d7aea774d7a39439fd72ff2eb1a8b7271cba573c7b62e2ec824e" } } ], "extra": [ 1, 226, 171, 254, 254, 237, 94, 15, 35, 68, 31, 51, 92, 207, 3, 98, 117, 222, 181, 248, 188, 69, 172, 43, 203, 154, 202, 180, 219, 134, 102, 153, 125, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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