Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a388296f351404ecbdfd3c0f9b625434c1f217f617b1b44368fdf7073162408

Tx prefix hash: 274e66acd002ed5668593f8f85a9f986fa54d94a8ae43e156d2d79c3b32f783b
Tx public key: 044f5c7bd7f06c3475c521ad8630c7599d5aae929d078babdf3811f19c196461
Timestamp: 1718668854 Timestamp [UCT]: 2024-06-18 00:00:54 Age [y:d:h:m:s]: 01:146:15:05:53
Block: 1046520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363351 RingCT/type: yes/0
Extra: 01044f5c7bd7f06c3475c521ad8630c7599d5aae929d078babdf3811f19c1964610211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea5f5a55636c1711afedc240f17d607938e9a8397e893fc875fca55e5dd2891b 0.600000000000 1516335 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": 1046530, "vin": [ { "gen": { "height": 1046520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea5f5a55636c1711afedc240f17d607938e9a8397e893fc875fca55e5dd2891b" } } ], "extra": [ 1, 4, 79, 92, 123, 215, 240, 108, 52, 117, 197, 33, 173, 134, 48, 199, 89, 157, 90, 174, 146, 157, 7, 139, 171, 223, 56, 17, 241, 156, 25, 100, 97, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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