Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7889f173ff7dccfe8b05c83c5d8f6814426d703c1ffcfed685ab7433a606b85b

Tx prefix hash: 5147f75165e3b7ca2f5f3bf42635a1703fcfe11ae9b7ca7df56209bc7f930abf
Tx public key: 2caa324300bcd351b61fe1d6e546905fbc5da4666423b5043d431957a1d51b5d
Timestamp: 1705386717 Timestamp [UCT]: 2024-01-16 06:31:57 Age [y:d:h:m:s]: 01:298:13:08:56
Block: 936372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472211 RingCT/type: yes/0
Extra: 012caa324300bcd351b61fe1d6e546905fbc5da4666423b5043d431957a1d51b5d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c36e290de4633959a0f3d9fb9ff0fcdc31531c43eb00d3e4a75ed2a55f71ac7a 0.600000000000 1394396 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": 936382, "vin": [ { "gen": { "height": 936372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c36e290de4633959a0f3d9fb9ff0fcdc31531c43eb00d3e4a75ed2a55f71ac7a" } } ], "extra": [ 1, 44, 170, 50, 67, 0, 188, 211, 81, 182, 31, 225, 214, 229, 70, 144, 95, 188, 93, 164, 102, 100, 35, 181, 4, 61, 67, 25, 87, 161, 213, 27, 93, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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