Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c85ec2afdcad69040020dc29bc1ca41f4f333c121bb0f9a7f20a573e4c81968a

Tx prefix hash: dd5c3c0792a6c2f1b5d8e39d5396906417712e105b11e5f4ce7573e127abdf85
Tx public key: 2915abcdc8a89b36561b2ecced392eaf153525a813b3821f73f86061aaead8e9
Timestamp: 1712219490 Timestamp [UCT]: 2024-04-04 08:31:30 Age [y:d:h:m:s]: 00:279:21:03:42
Block: 993021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200373 RingCT/type: yes/0
Extra: 012915abcdc8a89b36561b2ecced392eaf153525a813b3821f73f86061aaead8e90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48e6900ca3628d0353f8c41cb5518bfebd0bf4e3e0444bb84a3fe3ae25671776 0.600000000000 1453399 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": 993031, "vin": [ { "gen": { "height": 993021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48e6900ca3628d0353f8c41cb5518bfebd0bf4e3e0444bb84a3fe3ae25671776" } } ], "extra": [ 1, 41, 21, 171, 205, 200, 168, 155, 54, 86, 27, 46, 204, 237, 57, 46, 175, 21, 53, 37, 168, 19, 179, 130, 31, 115, 248, 96, 97, 170, 234, 216, 233, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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