Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b39f11856128c0517f1a48e0866301d3b1c62902c0cc060c71d0f6417392f7a4

Tx prefix hash: a237b5b2a9b50f4b78ef0d2e3c982416db6ab73ca20ba12a88ae2c00adebf16b
Tx public key: ed122b55c6391821ecc0b5ff79f8f0c45be452b0db78120c80cdce717a52651a
Timestamp: 1710980996 Timestamp [UCT]: 2024-03-21 00:29:56 Age [y:d:h:m:s]: 01:017:17:17:05
Block: 982808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273607 RingCT/type: yes/0
Extra: 01ed122b55c6391821ecc0b5ff79f8f0c45be452b0db78120c80cdce717a52651a02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5a93e639e9da86c51e3e549847ddcbbe8f193d83af5fea23ccd69b7a378b50 0.600000000000 1442919 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": 982818, "vin": [ { "gen": { "height": 982808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5a93e639e9da86c51e3e549847ddcbbe8f193d83af5fea23ccd69b7a378b50" } } ], "extra": [ 1, 237, 18, 43, 85, 198, 57, 24, 33, 236, 192, 181, 255, 121, 248, 240, 196, 91, 228, 82, 176, 219, 120, 18, 12, 128, 205, 206, 113, 122, 82, 101, 26, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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