Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199c50c00b3bf120d14ecc6c2670838e8a0cd8876217a591c7a369256113c03c

Tx prefix hash: 7753bc0fc8c1a61b4ff78b8961f8142e88b91fe2b9d6d5045123c6ceb8f3d420
Tx public key: 648ee99ae53240dfb09207272e203aa9186320ba3bdd2c185622a94274e8343a
Timestamp: 1576425601 Timestamp [UCT]: 2019-12-15 16:00:01 Age [y:d:h:m:s]: 04:350:10:42:14
Block: 27555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136416 RingCT/type: yes/0
Extra: 01648ee99ae53240dfb09207272e203aa9186320ba3bdd2c185622a94274e8343a021100000013ad433a0b000000000000000000

1 output(s) for total of 497.393049541000 dcy

stealth address amount amount idx
00: 236f47c8a7e77afed0793b7222ea43c9c08910f9e4e3b105a12f84be492a784f 497.393049541000 45567 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": 27565, "vin": [ { "gen": { "height": 27555 } } ], "vout": [ { "amount": 497393049541, "target": { "key": "236f47c8a7e77afed0793b7222ea43c9c08910f9e4e3b105a12f84be492a784f" } } ], "extra": [ 1, 100, 142, 233, 154, 229, 50, 64, 223, 176, 146, 7, 39, 46, 32, 58, 169, 24, 99, 32, 186, 59, 221, 44, 24, 86, 34, 169, 66, 116, 232, 52, 58, 2, 17, 0, 0, 0, 19, 173, 67, 58, 11, 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