Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eef712869ff5a96cf8d0f12534d8e01eb626b4ec0272a56dd0fccbf7451da4be

Tx prefix hash: 6ec8e5bb0a1904a3769b77e8e7cb130c680c5703552d7c4862ec8015560a6b00
Tx public key: 06b9c12543928f54ed797749979d52938fec034858ed1648bddc0e99b8fd6b6a
Timestamp: 1727172546 Timestamp [UCT]: 2024-09-24 10:09:06 Age [y:d:h:m:s]: 00:061:07:55:10
Block: 1117020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43830 RingCT/type: yes/0
Extra: 0106b9c12543928f54ed797749979d52938fec034858ed1648bddc0e99b8fd6b6a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 113ca8f1f31bedf50de2040c2f84e223a8a321e10f2d82d2c19cfefd8ae64e5c 0.600000000000 1597707 of 15

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": 1117030, "vin": [ { "gen": { "height": 1117020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "113ca8f1f31bedf50de2040c2f84e223a8a321e10f2d82d2c19cfefd8ae64e5c" } } ], "extra": [ 1, 6, 185, 193, 37, 67, 146, 143, 84, 237, 121, 119, 73, 151, 157, 82, 147, 143, 236, 3, 72, 88, 237, 22, 72, 189, 220, 14, 153, 184, 253, 107, 106, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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