Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675afe899c0150a67d0677b635b3dbc0a42241b1a77dcb6b3ef821200ee0981b

Tx prefix hash: 1d2a03e8ab66e37ac3122a3832029ac1a4356d288b26c5f53c398de0cbb5d00e
Tx public key: 7b8daf18f803abee10ed121d975ba53a7daf0a667b70d4b32a3d1f06bc7a73bd
Timestamp: 1713278375 Timestamp [UCT]: 2024-04-16 14:39:35 Age [y:d:h:m:s]: 01:012:00:36:42
Block: 1001810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269571 RingCT/type: yes/0
Extra: 017b8daf18f803abee10ed121d975ba53a7daf0a667b70d4b32a3d1f06bc7a73bd02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 229ff571dbdad9ef9fd561432272e260ec084eaa322be5ebb440300d85dff413 0.600000000000 1462322 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": 1001820, "vin": [ { "gen": { "height": 1001810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229ff571dbdad9ef9fd561432272e260ec084eaa322be5ebb440300d85dff413" } } ], "extra": [ 1, 123, 141, 175, 24, 248, 3, 171, 238, 16, 237, 18, 29, 151, 91, 165, 58, 125, 175, 10, 102, 123, 112, 212, 179, 42, 61, 31, 6, 188, 122, 115, 189, 2, 17, 0, 0, 0, 1, 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