Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 959f3630cc78eaf6a206e6306609a4a08429ed5dbf1dcfdb3f6c7214a20fb447

Tx prefix hash: 27e526a419605d301c0028e3c1f7f17b10cf29248bfc2a102e9b2d4c0cd06a32
Tx public key: 9e9dd20a0722a2ae00f458e4fb4087b11304cc0e3a63a332318ea6b45a4c337f
Timestamp: 1707662791 Timestamp [UCT]: 2024-02-11 14:46:31 Age [y:d:h:m:s]: 01:037:08:36:38
Block: 955265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287766 RingCT/type: yes/0
Extra: 019e9dd20a0722a2ae00f458e4fb4087b11304cc0e3a63a332318ea6b45a4c337f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d197ad8373f6e5295f9098f5a78a15de0a7c1312bb4ba02bf6fa3ae589ca401 0.600000000000 1414551 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": 955275, "vin": [ { "gen": { "height": 955265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d197ad8373f6e5295f9098f5a78a15de0a7c1312bb4ba02bf6fa3ae589ca401" } } ], "extra": [ 1, 158, 157, 210, 10, 7, 34, 162, 174, 0, 244, 88, 228, 251, 64, 135, 177, 19, 4, 204, 14, 58, 99, 163, 50, 49, 142, 166, 180, 90, 76, 51, 127, 2, 17, 0, 0, 0, 3, 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