Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43ea954ec10bbb31e788be2a97b5873ef4f3d4eb5f7a9f191ec4154fcb27832

Tx prefix hash: 655c8365c069f5b66eb1e6b32c213c6449460673e39aae55eab9ea340c515a2d
Tx public key: 04ef8ec19f17c370fb6024909291ad015b49a4d5ae53afe3c840a4ebc5e51c1c
Timestamp: 1638672168 Timestamp [UCT]: 2021-12-05 02:42:48 Age [y:d:h:m:s]: 03:028:03:32:43
Block: 388649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799033 RingCT/type: yes/0
Extra: 0104ef8ec19f17c370fb6024909291ad015b49a4d5ae53afe3c840a4ebc5e51c1c02110000000106faf294000000000000000000

1 output(s) for total of 31.640613461000 dcy

stealth address amount amount idx
00: 8fe062cf421dd11ede5fe7e9c00e90340416bdc1a4196d0db78ec4ca74948a68 31.640613461000 783414 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": 388659, "vin": [ { "gen": { "height": 388649 } } ], "vout": [ { "amount": 31640613461, "target": { "key": "8fe062cf421dd11ede5fe7e9c00e90340416bdc1a4196d0db78ec4ca74948a68" } } ], "extra": [ 1, 4, 239, 142, 193, 159, 23, 195, 112, 251, 96, 36, 144, 146, 145, 173, 1, 91, 73, 164, 213, 174, 83, 175, 227, 200, 64, 164, 235, 197, 229, 28, 28, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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