Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 851a810f9d2f6b7d5a2ca271b24797cdbd110376763d45d00735fd4e3ef18540

Tx prefix hash: e6467335865546476b5e4b98f3564466136a5b355b3e91750b60cce5b4a448c2
Tx public key: 274c92d368d948e215d3a4b7300b4781a087b24175e4ecaf109f7f8cc8029e96
Timestamp: 1731125660 Timestamp [UCT]: 2024-11-09 04:14:20 Age [y:d:h:m:s]: 00:197:01:46:14
Block: 1149711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140711 RingCT/type: yes/0
Extra: 01274c92d368d948e215d3a4b7300b4781a087b24175e4ecaf109f7f8cc8029e960211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57cdb2b14babd12afaf13492d1bfc4c4276bc7972c1a6ebc9f54a5ac42149cbf 0.600000000000 1634858 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": 1149721, "vin": [ { "gen": { "height": 1149711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57cdb2b14babd12afaf13492d1bfc4c4276bc7972c1a6ebc9f54a5ac42149cbf" } } ], "extra": [ 1, 39, 76, 146, 211, 104, 217, 72, 226, 21, 211, 164, 183, 48, 11, 71, 129, 160, 135, 178, 65, 117, 228, 236, 175, 16, 159, 127, 140, 200, 2, 158, 150, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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