Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6030f28e222e2cafa4c5f20510c9f59173c3e709d426536124a79c3480905f62

Tx prefix hash: be96c77eb26f29f32bee8c9dcbd2398485a3a228430b4e01fca03e66a1cb17bc
Tx public key: 8270f2fceaff09f97b7c614de79eb0f5146b06cab84036ed9f3a8cc4bcb92460
Timestamp: 1736555037 Timestamp [UCT]: 2025-01-11 00:23:57 Age [y:d:h:m:s]: 00:158:20:00:18
Block: 1194662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113221 RingCT/type: yes/0
Extra: 018270f2fceaff09f97b7c614de79eb0f5146b06cab84036ed9f3a8cc4bcb92460021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17261dd14c75dbca497814c4dc6ce84f5c961b26bda16c6c0f8e9b6f6842406c 0.600000000000 1681239 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": 1194672, "vin": [ { "gen": { "height": 1194662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17261dd14c75dbca497814c4dc6ce84f5c961b26bda16c6c0f8e9b6f6842406c" } } ], "extra": [ 1, 130, 112, 242, 252, 234, 255, 9, 249, 123, 124, 97, 77, 231, 158, 176, 245, 20, 107, 6, 202, 184, 64, 54, 237, 159, 58, 140, 196, 188, 185, 36, 96, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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