Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d98e540347d391244c79104b99446df3837b52f37ce040ace51789624d708d2

Tx prefix hash: b9ce1f9564ea1069b11c4bd5d38207d8f2ef368912ac90e9eb750b4eca67eaae
Tx public key: c01e83e69c9bffcc5779062eb325709225a9c9d9b0cc4dec4dd9aaef19652b7e
Timestamp: 1692297069 Timestamp [UCT]: 2023-08-17 18:31:09 Age [y:d:h:m:s]: 01:190:09:43:08
Block: 828044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397209 RingCT/type: yes/0
Extra: 01c01e83e69c9bffcc5779062eb325709225a9c9d9b0cc4dec4dd9aaef19652b7e02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.107507254000 dcy

stealth address amount amount idx
00: 539156e384df060a2242fae6a6def23cdba8067912dc888ec03f125b537064ea 1.107507254000 1280364 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": 828054, "vin": [ { "gen": { "height": 828044 } } ], "vout": [ { "amount": 1107507254, "target": { "key": "539156e384df060a2242fae6a6def23cdba8067912dc888ec03f125b537064ea" } } ], "extra": [ 1, 192, 30, 131, 230, 156, 155, 255, 204, 87, 121, 6, 46, 179, 37, 112, 146, 37, 169, 201, 217, 176, 204, 77, 236, 77, 217, 170, 239, 25, 101, 43, 126, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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