Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52aff53e2e77e756c27dd184bb79dc869114ab2aff08a3404169e506ca10f461

Tx prefix hash: c7cb4f22165a58c522fdbf4d85c6cb42d45fd99f96eed996f9e8aea15510ea2b
Tx public key: 6f6b5da147b2357ad909ba6ef64059f2f62fc505d7bea231d0282d88e80ffb4f
Timestamp: 1701844600 Timestamp [UCT]: 2023-12-06 06:36:40 Age [y:d:h:m:s]: 01:102:05:33:37
Block: 907032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334232 RingCT/type: yes/0
Extra: 016f6b5da147b2357ad909ba6ef64059f2f62fc505d7bea231d0282d88e80ffb4f02110000000333af99f4000000000000000000

1 output(s) for total of 0.606214654000 dcy

stealth address amount amount idx
00: a10c5a127e3c3c983827bbdf9f4d1238e6c6d8de86a0aa3c1496df5ba4ab3720 0.606214654000 1363995 of 0

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": 907042, "vin": [ { "gen": { "height": 907032 } } ], "vout": [ { "amount": 606214654, "target": { "key": "a10c5a127e3c3c983827bbdf9f4d1238e6c6d8de86a0aa3c1496df5ba4ab3720" } } ], "extra": [ 1, 111, 107, 93, 161, 71, 178, 53, 122, 217, 9, 186, 110, 246, 64, 89, 242, 246, 47, 197, 5, 215, 190, 162, 49, 208, 40, 45, 136, 232, 15, 251, 79, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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