Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6112b342ed91a2879bd464b768973d066e18de2570230bb0b58dc58c81bfb9eb

Tx prefix hash: 727dbe3751fba5ca07c1c838918c496c82a066b5fd9dbc922ce942a310d26dfc
Tx public key: d331430fd9304dabcf00c9e091e88ce0013fa2986248f7aeec2f8b10c295467d
Timestamp: 1729157747 Timestamp [UCT]: 2024-10-17 09:35:47 Age [y:d:h:m:s]: 00:148:12:32:35
Block: 1133483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105925 RingCT/type: yes/0
Extra: 01d331430fd9304dabcf00c9e091e88ce0013fa2986248f7aeec2f8b10c295467d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe06f29926fcfc0a6f4ac60061dbb8e6f1a1ae3c6bbe3101d934f731b264fe97 0.600000000000 1616606 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": 1133493, "vin": [ { "gen": { "height": 1133483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe06f29926fcfc0a6f4ac60061dbb8e6f1a1ae3c6bbe3101d934f731b264fe97" } } ], "extra": [ 1, 211, 49, 67, 15, 217, 48, 77, 171, 207, 0, 201, 224, 145, 232, 140, 224, 1, 63, 162, 152, 98, 72, 247, 174, 236, 47, 139, 16, 194, 149, 70, 125, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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