Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6451d425a311d3fb80334be2ef5d24be49c7a0a9f33d3a638ac390e5ebf46c4

Tx prefix hash: 8de50d16dc91421183d70cd0aad784cfc2d352ef91b8187d997c62c3b46c40a3
Tx public key: 97bef49bb21aa3017f787bd96d30ae2112f4e7d544f08cc9c360a71a2aee0ba2
Timestamp: 1736975201 Timestamp [UCT]: 2025-01-15 21:06:41 Age [y:d:h:m:s]: 00:153:19:20:49
Block: 1198136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109630 RingCT/type: yes/0
Extra: 0197bef49bb21aa3017f787bd96d30ae2112f4e7d544f08cc9c360a71a2aee0ba2021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 009748a9cea2978b2e61dd77bba1b4335d98d1fc92dbb8e84e817b572330cbb8 0.600000000000 1684755 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": 1198146, "vin": [ { "gen": { "height": 1198136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "009748a9cea2978b2e61dd77bba1b4335d98d1fc92dbb8e84e817b572330cbb8" } } ], "extra": [ 1, 151, 190, 244, 155, 178, 26, 163, 1, 127, 120, 123, 217, 109, 48, 174, 33, 18, 244, 231, 213, 68, 240, 140, 201, 195, 96, 167, 26, 42, 238, 11, 162, 2, 17, 0, 0, 0, 8, 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