Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ef46d3600e2fb87f5bb10c06c5f8a903bd600e9b909bfd74d11179af8b0825

Tx prefix hash: 9da36422885c1f30e3f0df5ae9ea55982a35e126dbf95d16125c8a99fabee022
Tx public key: 4c16f8910701c1041fded63dbe8b9279da8b3e785c416da11db3c2a485ca4a56
Timestamp: 1737811960 Timestamp [UCT]: 2025-01-25 13:32:40 Age [y:d:h:m:s]: 00:331:22:54:27
Block: 1205027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234831 RingCT/type: yes/0
Extra: 014c16f8910701c1041fded63dbe8b9279da8b3e785c416da11db3c2a485ca4a56021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 197d1bccb85167d102ca0382be46b8ab01df2d815f3c2d09942646af4888da5b 0.600000000000 1691724 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": 1205037, "vin": [ { "gen": { "height": 1205027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "197d1bccb85167d102ca0382be46b8ab01df2d815f3c2d09942646af4888da5b" } } ], "extra": [ 1, 76, 22, 248, 145, 7, 1, 193, 4, 31, 222, 214, 61, 190, 139, 146, 121, 218, 139, 62, 120, 92, 65, 109, 161, 29, 179, 194, 164, 133, 202, 74, 86, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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