Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d040067b6b407a41a6931dd003323e937129ef2a0f74865b2d4241d396fcb86

Tx prefix hash: 4a902b296873a9c53fc8f9a76159cfabc6d082d20dcf7dff3489c5796d665dc9
Tx public key: 0c8cb14c723523a23683a8fcc4376cf7ba2f14cfff3f7855c93f62aba0f47bfe
Timestamp: 1698417040 Timestamp [UCT]: 2023-10-27 14:30:40 Age [y:d:h:m:s]: 01:169:08:21:40
Block: 878839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382049 RingCT/type: yes/0
Extra: 010c8cb14c723523a23683a8fcc4376cf7ba2f14cfff3f7855c93f62aba0f47bfe0211000000024b8f5122000000000000000000

1 output(s) for total of 0.751694866000 dcy

stealth address amount amount idx
00: 24f2e5520e2c0c4b291e85b5c7e0193a3ea5793c5f58de3e8e6f37dbca863ebf 0.751694866000 1334327 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": 878849, "vin": [ { "gen": { "height": 878839 } } ], "vout": [ { "amount": 751694866, "target": { "key": "24f2e5520e2c0c4b291e85b5c7e0193a3ea5793c5f58de3e8e6f37dbca863ebf" } } ], "extra": [ 1, 12, 140, 177, 76, 114, 53, 35, 162, 54, 131, 168, 252, 196, 55, 108, 247, 186, 47, 20, 207, 255, 63, 120, 85, 201, 63, 98, 171, 160, 244, 123, 254, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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