Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f3e9ba82715b120caaec365690746e62e098666c20b6cd3eeda0fba0e87cfad

Tx prefix hash: 502b4d2cd946c920e87a16d1b5e63306aa8b6e4f2ce7229fc42918af92b56b3a
Tx public key: a47fe8b034d28beeff2fcce4bf25c650ee669e3125f754e77b497356bae2eadd
Timestamp: 1713444759 Timestamp [UCT]: 2024-04-18 12:52:39 Age [y:d:h:m:s]: 00:209:21:17:09
Block: 1003194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150264 RingCT/type: yes/0
Extra: 01a47fe8b034d28beeff2fcce4bf25c650ee669e3125f754e77b497356bae2eadd02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4fb0b453d28f290e21af2f1d7afe3b8f25dfe0ca468ae595b9cea4e01fe54d4 0.600000000000 1463724 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": 1003204, "vin": [ { "gen": { "height": 1003194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4fb0b453d28f290e21af2f1d7afe3b8f25dfe0ca468ae595b9cea4e01fe54d4" } } ], "extra": [ 1, 164, 127, 232, 176, 52, 210, 139, 238, 255, 47, 204, 228, 191, 37, 198, 80, 238, 102, 158, 49, 37, 247, 84, 231, 123, 73, 115, 86, 186, 226, 234, 221, 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