Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d570dee63c013df74e64357056d8e1f71d4e5db9eec2b8ef34c2877f61dec3b

Tx prefix hash: 696ff70bb5e8d0df482ec599c5fb64f1bef1e55196d7fde546de899b6827e079
Tx public key: 656a3265820b274a91011e6a371cd9446d52db382f51dc4a7d54d97eacf2cdf8
Timestamp: 1722818010 Timestamp [UCT]: 2024-08-05 00:33:30 Age [y:d:h:m:s]: 00:224:02:22:53
Block: 1080912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160062 RingCT/type: yes/0
Extra: 01656a3265820b274a91011e6a371cd9446d52db382f51dc4a7d54d97eacf2cdf802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ecae23e6ad13921550e900ff79790780c5f798699783fe782311ef2c30bf8b 0.600000000000 1554455 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": 1080922, "vin": [ { "gen": { "height": 1080912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ecae23e6ad13921550e900ff79790780c5f798699783fe782311ef2c30bf8b" } } ], "extra": [ 1, 101, 106, 50, 101, 130, 11, 39, 74, 145, 1, 30, 106, 55, 28, 217, 68, 109, 82, 219, 56, 47, 81, 220, 74, 125, 84, 217, 126, 172, 242, 205, 248, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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