Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a976354a457b61ba1a8ce6bd7e74b44740026ef1199860f4b5229aad06c160

Tx prefix hash: 1cf641ae3ad16ca3b75361cde0ed07e747d21ac9cd1ce7c5bab6c3b2383a87e0
Tx public key: f238c69d4a6778f02dcf3f6be5527dede654c2ff85cea6efdf48f0e92a3ee4ba
Timestamp: 1577734628 Timestamp [UCT]: 2019-12-30 19:37:08 Age [y:d:h:m:s]: 04:311:19:53:25
Block: 35283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111894 RingCT/type: yes/0
Extra: 01f238c69d4a6778f02dcf3f6be5527dede654c2ff85cea6efdf48f0e92a3ee4ba0211000000098a2ee0d9000000000000000000

1 output(s) for total of 468.914463792000 dcy

stealth address amount amount idx
00: 29f5ccdb407f9f2f6d19b24d8627d92919e31caa7c5c47e33041eca1991789a8 468.914463792000 59415 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": 35293, "vin": [ { "gen": { "height": 35283 } } ], "vout": [ { "amount": 468914463792, "target": { "key": "29f5ccdb407f9f2f6d19b24d8627d92919e31caa7c5c47e33041eca1991789a8" } } ], "extra": [ 1, 242, 56, 198, 157, 74, 103, 120, 240, 45, 207, 63, 107, 229, 82, 125, 237, 230, 84, 194, 255, 133, 206, 166, 239, 223, 72, 240, 233, 42, 62, 228, 186, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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