Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f11d253fed456cb35a4b800305330cd4545500859dd7418cbf66f62d18b924b2

Tx prefix hash: 7d652f4c3f33dbb3d86f9369681da30913fb6ed1a9c34c588ea9c52b06221c73
Tx public key: 8c425fb8c73672b3ef25fbfb901d1e613fe763a869f931e0a6730770f99cc265
Timestamp: 1738522559 Timestamp [UCT]: 2025-02-02 18:55:59 Age [y:d:h:m:s]: 00:338:05:24:31
Block: 1210679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239566 RingCT/type: yes/0
Extra: 018c425fb8c73672b3ef25fbfb901d1e613fe763a869f931e0a6730770f99cc2650211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6e7a0d4b7a3944035778b99a92fe3abaf7f4fccc534e1fbbf178fa65f01e014 0.600000000000 1697432 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": 1210689, "vin": [ { "gen": { "height": 1210679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6e7a0d4b7a3944035778b99a92fe3abaf7f4fccc534e1fbbf178fa65f01e014" } } ], "extra": [ 1, 140, 66, 95, 184, 199, 54, 114, 179, 239, 37, 251, 251, 144, 29, 30, 97, 63, 231, 99, 168, 105, 249, 49, 224, 166, 115, 7, 112, 249, 156, 194, 101, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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