Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fd89df9fa6d46c1c1ec76028ddaeb6f5dfcc7c8cbdb0574ae1a7695c4b32e7a

Tx prefix hash: 69dffd1fb0236e5275aa166ceab1db984c36cf790da96c70e15ad4e2daaf8244
Tx public key: b890772ff519fa2bf343f5004f537a2159e826a763fee6304c1b241ac24896cc
Timestamp: 1706408598 Timestamp [UCT]: 2024-01-28 02:23:18 Age [y:d:h:m:s]: 01:081:03:59:33
Block: 944849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319105 RingCT/type: yes/0
Extra: 01b890772ff519fa2bf343f5004f537a2159e826a763fee6304c1b241ac24896cc02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2113c0f9cc5cbaecfd5282971bf9d4e808f0e21ca78f69a8ed44eb7b67b753f 0.600000000000 1403137 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": 944859, "vin": [ { "gen": { "height": 944849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2113c0f9cc5cbaecfd5282971bf9d4e808f0e21ca78f69a8ed44eb7b67b753f" } } ], "extra": [ 1, 184, 144, 119, 47, 245, 25, 250, 43, 243, 67, 245, 0, 79, 83, 122, 33, 89, 232, 38, 167, 99, 254, 230, 48, 76, 27, 36, 26, 194, 72, 150, 204, 2, 17, 0, 0, 0, 5, 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