Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e91cd1a147f94a8ed06c508b31d84464cf1e41ed5a4dc82ab44c1570b0867871

Tx prefix hash: be1e7dfe583a312d1bf4f674f069312e212c1946c4fdca0ccda64a607524899a
Tx public key: 2f1b2832826f87f2d77305f8c664582a74f6390c2bc49d52c73af3657227c4aa
Timestamp: 1706206659 Timestamp [UCT]: 2024-01-25 18:17:39 Age [y:d:h:m:s]: 01:281:07:49:08
Block: 943171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459873 RingCT/type: yes/0
Extra: 012f1b2832826f87f2d77305f8c664582a74f6390c2bc49d52c73af3657227c4aa02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1a1f51134769ebe86efd1583fee8d4c1d1bf66aa1e943d89334aac91ff4aec 0.600000000000 1401371 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": 943181, "vin": [ { "gen": { "height": 943171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1a1f51134769ebe86efd1583fee8d4c1d1bf66aa1e943d89334aac91ff4aec" } } ], "extra": [ 1, 47, 27, 40, 50, 130, 111, 135, 242, 215, 115, 5, 248, 198, 100, 88, 42, 116, 246, 57, 12, 43, 196, 157, 82, 199, 58, 243, 101, 114, 39, 196, 170, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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